About Security Permissions - Organization Work Area

In the Organization work area, you can set permissions for security roles and company roles.

Security Setting Applies to Security Roles - Yes (Y)/No (N) Applies to Company Roles - Yes (Y)/No (N)
Accounts Y Y
Bid History Y Y
Bond (Org Company) Y Y
Bond (Company) Y Y

Business Unit

Y Y

Calendar

Y Y
Catalog Card Y Y
Certification (Company) Y Y
Certification (Org Company) Y Y

Company#

Y Y

Contact#

Y Y
Contract History Y Y
Copy Context Data Y Y
Cost Setting Y Y
Currency Y Y

Custom Print Layout Document

Y Y
Distribution List Y Y

External Report

Y Y

Insurance (Company)

Y Y
Insurance (Org Company) Y Y
Languages Y Y
License and Login Reporting Y Y
Location (Company) Y Y
Lookup Management N Y
Location (Org Company, Business Unit) Y Y
Manage Web Service Queries Y Y
OAuth Configuration Y Y
Org Company Y Y
Password Policy Y Y
Plan Package Y Y

Portfolio Properties

Y Y
Review Process Y Y
Security Permissions* Y Y
Shared Views Y Y
Staff Y Y
Standard Form Y Y
Standard Plan Y Y
Workspace Properties Y Y
Workspace Summary N Y

#Companies and Contacts: Without permission to read companies and contacts, users are very restricted in Proliance. For users to perform even basic actions, such as forwarding documents or selecting recipients for collaboration, their security role must have read permission to companies and contacts.

*Security Permissions is not an actual document type. Rather, it represents settings that affect all the security-related registers: Roles, Categories, and Company Roles. For more information, see "Restricting Access to Security".

**The Custom Culture Entries permission is used to prevent users from updating the Web UI nomenclature when accessing Proliance through the Configuration Web service.